Why Games Are Good For Business by Helen Routledge

Author:Helen Routledge [Helen Routledge]
Language: eng
Format: epub
ISBN: 9781137448965
Publisher: Palgrave macmillan

High-level design

Goal: to create a design document expanding on the chosen concept which captures all critical functionality from a descriptive point of view.

Prerequisites: a locked-down and agreed to concept has been selected and the scope has been agreed.

What happens here? We choose to break down our design deliverable into two stages. The high-level design is stage one. This document is created by the design team, consisting of instructional designers, technical lead and art lead. The high-level design develops the concept design into a key functional specification. The output of this phase is the high-level design document which will clearly outline the nature of the application, how the learning outcomes are mapped to the activities, the audience demographics, key functionality and proposed visual style. We often bring into play a use case approach to “tell the story” of the application from the users’ perspective.

The high-level design is always sense-checked with the project manager and technical lead to ensure the proposed design can be met within project schedule.

The high-level design is then provided to the client for review and iteration until all requirements and functionality are clearly defined and all parties have a clear understanding of the application to be developed.

Outcome: this stage culminates with the acceptance by you, the client, of the final version of this document. Of course, in an ideal world this document would remain frozen and unchanged through the lifecycle of the project. However, that is often a pipe dream and no project will ever completely avoid scope creep, but by setting some parameters, the project team can begin to track any scope creep or changes quickly and easily through document iteration. Without this starting point it is very difficult to manage scope moving forward.

Follow on actions: any changes made to the project scope are also documented here. I suggest adding a change log to the start of the document, highlighting what the change is, who requested it, who agreed to it, what it affects and what page the change can be found on. This is vitally important as this is the document you will often be evaluating the final application against. If this is not kept up to date, UAT is a lot trickier.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.